Skip to content

Conversation

@arlesniak
Copy link

Enable optim_bf16_stochastic_round_correctness test for XPU

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 24, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/3055

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ No Failures

As of commit b1121ac with merge base f92b898 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 24, 2025
torch.testing.assert_close(p2, p1)

@parametrize("device", _DEVICES)
def test_optim_bf16_stochastic_round_correctness(self):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

device arg is not added to the function

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@arlesniak _DEVICES is the global variable in this file, I don't think your change is needed.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "test_optim_bf16_stochastic_round_correctness" should be parametrized with _DEVICES global variable, which contains other devices (XPU if detected). Without the PR changes the choice was cuda, cpu only.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure? According to this code,https://github.com/pytorch/ao/blob/main/torchao/utils.py#L143 when the xpu is available in your ENV, the _DEVICES will contain the XPU.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me be more precise. You're right, the _DEVICES list will contain XPU if detected. Without the PR changes the test will be triggered once with the hardcoded device choice - cuda or cpu: https://github.com/pytorch/ao/blob/main/test/test_low_bit_optim.py#L423, regardless of _DEVICES content.
After the PR changes, the test will be triggered separately for every device from the _DEVICES including XPU (similiar to some other parametrized tests i.e. test_quantize_8bit_with_qmap_correctness etc).

@liangan1 liangan1 self-requested a review September 29, 2025 07:08
@arlesniak arlesniak force-pushed the arlesniak/enable_optim_sr_test_xpu branch from cfd22f6 to b1121ac Compare October 22, 2025 13:26
@liangan1 liangan1 added topic: improvement Use this tag if this PR is an improvement (doesn't fit into any of the other categories) ciflow/xpu label used to trigger xpu CI jobs labels Nov 4, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Nov 4, 2025

To add the ciflow label ciflow/xpu please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

@pytorch-bot pytorch-bot bot removed the ciflow/xpu label used to trigger xpu CI jobs label Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. topic: improvement Use this tag if this PR is an improvement (doesn't fit into any of the other categories)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants